An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi everyone, Our app (version 1.0, first-time submission) has been in "Waiting for Review" status since May 8, 2026 — it has now been 20 days with no movement to "In Review". Some context: This is an educational app built to support our language education center's daily operations (attendance, assignments, learning progress, and internal management for students, teachers, and staff). The submitted build is complete and ready for review. Demo account credentials are provided in App Review Information and are active. Our backend services are stable and accessible for testing at any time. What I've already tried: Opened a support case and received responses confirming the submission is in queue and that reviewers have been notified. Submitted an expedited review request, which was accepted — but the status has not changed. Followed up multiple times, but the most recent replies have been identical template responses with no specific update. I understand review times can vary, but 20 days significantly exceeds the typical 24–48 hour window. I've also noticed several recent forum posts describing similar extended delays, so I'm wondering whether this is part of a broader issue or something specific to my submission. Has anyone experienced similar delays recently? Are there any additional steps I could take, or any insight from the App Review team would be greatly appreciated. Thank you.

Hello App Review Team, My app update has been stuck in "Waiting for Review" for 8+ days with no progress. Previous submissions for this app were reviewed within 24–48 hours, so this delay is unusual. Apple ID: 1666011539 Bundle ID: art.dreamerai.ios Version: 1.62.0 Submitted: May 20, 2026 Status: Waiting for Review We have already tried every available channel: 2 Expedited Review requests submitted — both ignored, no progress Emailed App Review asking for status — no reply This is a major update with critical bug fixes and major new features that our existing users are actively asking about. Our marketing campaign around the launch has already been delayed because of this hold. The build is fully compliant with the Review Guidelines — no new entitlements, no new SDKs, no changes to data collection. Happy to provide any additional info needed. Any help from the App Review team would be greatly appreciated. Thank you.

Hi everyone! Today I finally submitted my first iOS app for App Store review after previously publishing the Android version on Google Play. App ID: 6771439707 The app was developed with Flutter and the process was a very interesting learning experience, especially around: App Privacy configuration screenshots and metadata archive/distribution process App Store Connect setup adapting branding/assets to platform guidelines Coming from Android publishing, I have to admit the Apple review pipeline feels much stricter and more detail-oriented 😄 but also very polished once everything is correctly configured. I just wanted to thank the community because many forum posts helped me solve issues during the submission process. Now waiting for review results 🤞 Greetings from Argentina!

Hello Apple App Review Team, I am writing to urgently request your assistance regarding our application 'Kavra'. We are facing a critical situation that is heavily impacting our entire launch roadmap and user base. To give you the timeline: we initially submitted the app for review on April 30th. After waiting for two full weeks without any updates or status changes, we assumed there might be a technical stall in the review pipeline. Consequently, we canceled the submission and resubmitted the app on May 14th. Today is May 27th, and the application has been stuck in the "Waiting for Review" status for another 13 days. In total, we have been locked in the review queue for nearly a month. This prolonged delay has completely frozen our development cycle and disrupted our time-sensitive marketing plans. We have thoroughly audited our app against all App Store Review Guidelines and confirm 100% compliance. There should be no blockers from our end. If you require any additional information, test accounts, or documentation to move this forward, please let me know immediately. We kindly request you to look into our account for any technical glitches and expedite the review process. Thank you very much for your time, understanding, and support. Sincerely, [Bora Çoban]

Hi, My app submission has been waiting for review for an unusually long time after submission. This update is very important for us because it is related to payments. At the moment, a payment-related issue is preventing us from properly collecting revenue, so this is becoming a critical problem for our business. I submitted a request for an expedited review, but so far I have not received any action or update. I do not use the expedited review option often - only when there is a genuinely critical issue that needs to be resolved quickly. Could someone from Apple advise whether this waiting time is normal, or if there is anything I should check or do on my side? I can provide the Submission ID privately if needed. Thank you.

I'm in need of some guidance regarding an issue I'm facing with the App Store review process. My app was recently rejected in the Kids Category due to the following error: Guideline 1.3 - Safety - Kids Category "We still noticed that you have not provided any publicly documented practices and policies for third-party contextual advertising in your Kids Category app." I'm somewhat perplexed by this rejection because a previous version of my app, which also included ads, was accepted without any problems. I'm using AdMob and have configured it to serve only child-appropriate ads while blocking any content that may not be suitable for children . The issue is that I'm not entirely sure what specific documentation or policies Apple is looking for in this regard. I would greatly appreciate any guidance or advice from the community on what I need to provide to address this concern and resubmit my app for review successfully. Has anyone experienced a similar situation, or can anyone offer insights into what might be required for compliance with this guideline? Your assistance and insights would be immensely helpful, and I'm committed to making the necessary adjustments to ensure my app meets the guidelines for the Kids Category. Thank you in advance for your support and suggestions.

Hello App Review Team, I am following up on my earlier post about our app (App ID: 6761247061), as our situation has unfortunately not improved. Our app was finally reviewed on May 22 and rejected under Guideline 2.1(a). We resolved the issue on the same day and resubmitted, but the resubmission has been stuck in "Waiting for Review" again for several business days with no progress. Due to these repeated delays, we have been unable to release a new version of our app to our users for nearly three weeks. If there is anything we are missing, or any issue with our submission that we should address, we sincerely ask for your guidance. We are fully committed to complying with the Review Guidelines and resolving any concerns you may have. Any guidance from your team would mean so much to us. Thank you so much for your time and patience.

Hello, My app was submitted for review last week, but it is still showing the status Waiting for Review and has not moved into the review process yet. App details: App ID: 6751946791 Current status: Waiting for Review Submission time: Last week Additional context: Due to a time-sensitive launch schedule, I have submitted several expedited review requests, but the app status has not changed. I would like to ask: Could submitting multiple expedited review requests affect the normal review queue or delay the review process? Does staying in Waiting for Review for this long indicate any possible issue with the submission, metadata, account status, or review queue? If further follow-up is needed, should I contact the App Review team through the App Review contact form? Any guidance from Apple or developers with similar experience would be greatly appreciated. Thank you.

My app "Fun Games - Mini Offline Games" (ID: 6761358642) has been in "Waiting for Review" for over a month. Apple Support told me on May 19 it was being expedited, but there's been no change for 8 days since. This is delaying our marketing campaign and causing financial loss. Could the App Review team please investigate or reach out? Thank you.

Hi everyone, We are experiencing a bizarre issue with one of our apps, BLOKX. Here is the quick timeline: March 26: First submission. No status change for 2 weeks. We canceled and resubmitted. April 27: Still zero movement. We updated our SDK and submitted again on May 15. On the exact same day, we submitted other app from our developer account. It got reviewed and approved. Only BLOKX gets completely ignored. May 20: Suspecting a technical glitch with the specific App ID, we created a brand new App ID and submitted BLOKX as a completely fresh app. Today (May 27): Still stuck in "Waiting for Review" with zero movement. The Support Loop: We have already contacted Apple Support multiple times regarding the old App ID (Case ID: 102871846091 and Case ID: 102875670447). The replies we are getting are incredibly frustrating and factually incorrect. Support keeps replying with a generic template stating that the app “was just submitted today” (matching the exact date of their email reply), completely ignoring the weeks it spent waiting. When we replied back with actual screenshots of our timeline and submission history proving otherwise, they simply copy-pasted the exact same response a few days later, just changing the date to the current day. • App name: BLOKX • Platform: iOS • Current status: Waiting for Review • Total waiting time: Almost 2 months (across both IDs) • Old App ID: 6761107868 • Current App ID: 6771268940 Has anyone faced something similar recently? How did you get Apple to notice? If any Apple engineering or forum moderator can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thanks in advance!

I recently noticed that an app called Private Browsing Web Browser has been ranking at the top for the keyword “browser” on the App Store for a long time, even ahead of well-known browsers like Chrome, Firefox, and Safari. This is not only the case in the U.S.; it also appears to rank top in many other regions. This app has not been updated for a long time, and both its interface and feature set seem extremely basic. There also appears to be nobody to discuss it on the internet, and some of the App Store ratings look very suspicious. I previously reported this to the Apple team by email, and questioning about the algorithm, but they consistently responded: The App Store ranking system has no problem, and it's working as expected.” I wanted to ask everyone: Do you think it is normal for this app to rank number one for “browser” on the App Store? Also, the same developer has another very similar browser app called Snowbunny Private Web Browser, which also ranked high.

I am in the middle of trying to get an app approved for beta release and the back and forth with the App Store reviewers has been incredibly frustrating and concerning. On Tuesday, I created an app record for my app but quickly realized I made it under the wrong account- I'm working for a company that has a few brands under it's umbrella, and I was under the wrong account when I created the app record. Rather than wait several days to get Apple's approval to transfer app ownership, I decided to delete that app record and create a new one under the proper account. Worst mistake of my life. Now, Apple is insisting that the new app record is spam despite my clarification that I own the other app record and that it was deleted before the new one was created. I have no choice but to believe that somebody else is using our branding and asset somewhere in the App Store that I can't see. Does anybody know how I can resolve this? It should have never taken me the whole week to make an app available on test flight and my stakeholders are not pleased, and I have no clear path towards resolution that will allow me to use the proper branding with the proper company account. App review refuse to offer any solutions, I am stuck with a brand name that I can't use because it's associated with an app I already deleted.

Hello Apple App Review Team, I am writing to urgently request your assistance. We have a strict, immovable launch deadline for our app on June 4. We initially submitted the app for review on May 15 and waited for 6 days without any response. Believing something might have gone wrong with the submission system, we self-rejected the binary, made a minor update, and resubmitted it on May 21. The app is currently still stuck in the "Waiting for Review" status. This launch is utterly important to us, and we absolutely cannot miss this deadline. If there is any additional information, documentation, or action required on our end to help expedite this process, please let me know immediately. Thank you very much for your time and support. Best regards, Pattaragorn (Phi) Xian Chiang

Hi everyone, We are facing an unusually long review delay for our iOS app submission. Our app has been in “Waiting for Review” status for almost 2 weeks now, with no update or movement. We had planned our official launch for 21 May 2026, but the launch date has already passed because the app is still not reviewed/approved. We have already contacted Apple Developer Support and requested assistance, but the status has not changed so far. For context: • App name: SuperWomen • Platform: iOS • Current status: Waiting for Review • Waiting time: Almost 2 weeks • Planned launch date affected: 21 May 2026 • Apple ID: 6759612459 • Case ID: 102898811179 Is anyone else still experiencing unusually long “Waiting for Review” times recently? Also, if Apple Staff can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thank you.

Hello everyone, I'm facing a very frustrating situation with App Review for my indie app, CoffeePomodoro, and I'm hoping someone here or an Apple engineer can help shed some light on how to escalate and resolve this. My recent update (Version 1.3.1, Submission ID: 59763b52-7c14-4b27-a2cf-2799d2bafe35) was rejected under Guideline 3.1.1 - In-App Purchase. The rejection message states: "We found that the app includes a feature to restore previously purchased In-App Purchase products by entering the user's Apple Account and password. However, In-App Purchases cannot be restored in this manner." The Reality: There is absolutely zero custom UI, form, or TextField in my app that asks for an Apple ID or password. When a user taps "Restore Purchases", the app simply calls Purchases.shared.restorePurchases() via the RevenueCat SDK, which directly wraps Apple's native SKPaymentQueue.restoreCompletedTransactions(). The credential prompt the reviewer saw is the native iOS system-level authentication dialog that appears automatically in the sandbox/TestFlight environment. This usually happens if the device or simulator being used for the review doesn't have an active Sandbox Apple ID already logged in. I have explained this in the App Store Connect Resolution Center. I provided screen recordings showing it's the system dialog, and I attached code snippets proving the app only calls native APIs. Unfortunately, my explanations seem to be ignored, and I keep facing the same roadblock. It feels like the reviewers are mistaking their own OS's native prompt for a custom credential-harvesting screen. Meanwhile, my users are waiting for this update to resolve their subscription issues, and I am stuck in a rejection loop for using Apple's own native API exactly as intended. Has anyone else experienced this specific misunderstanding by the review team? How can I escalate this so someone actually reviews the screen recording and code snippets I provided? Thank you for your time.

My app has been in "Waiting for Review" status since May 8, 2026, and today is May 25, 2026. Before this, I had another submission that was uploaded on April 26, 2026, which also remained pending for a long time. I assumed there may have been an issue on my side, so I removed it and submitted a new build on May 8 — but the new build is still waiting as well.

Hi Team, My app ICY SIM (App ID: 6761278922) has been stuck in "Waiting for Review" for over 4 weeks with no movement, no feedback, and no communication. What I've done: Submitted multiple expedited review requests and resubmissions (I now understand this can reset queue position, so I've stopped doing that) Filed a support ticket 3 days ago (Case ID: 102895038326) — still no response I completely understand the team handles a high volume of requests. However, 4 weeks with zero communication — not even an acknowledgment of the support ticket — is concerning. What I'd like to know: Is there a system glitch, account flag, or hidden blocker preventing my submission from entering review? Can someone confirm my app is actually in the queue and not stuck due to a technical issue? A queue position or estimated timeline would go a long way Any visibility from the App Review team or anyone who has experienced a similar situation would be greatly appreciated. Thank you.

Hi Apple, I hope you are doing well. I am posting here regarding our app, [Poker Reflex] (6761329446: [6761329446]), which has been stuck in the “Waiting for Review” state since [Friday 22th 2026]. We fully understand that App Review times can vary depending on workload and internal processes. However, in our case, the app has remained in this status for several days without any visible progress, update, rejection, metadata issue, or request for additional information. At the moment: No rejection message has been received No metadata issue is shown in App Store Connect No compliance or permission request appears to be pending No additional information has been requested from our side The app simply remains in “Waiting for Review” This is becoming a real concern for us because the delay is now significantly affecting our release planning and business timeline. We have carefully prepared the submission, reviewed the App Store Review Guidelines, and ensured that all required assets, metadata, permissions, and compliance information were provided. What concerns us most is that there seems to be no action or movement at all, which makes us wonder whether the submission may be stuck in the review queue or blocked by an unseen issue. We would sincerely appreciate any guidance from Apple or the developer community regarding: Whether this type of delay is currently common Whether there is any way to confirm that the app is properly queued for review Whether there may be an invisible issue preventing the review from starting Whether this can be escalated or checked by the App Review team We are fully available to provide any additional information or make immediate changes if something is required from our side. Any help, advice, or update would be greatly appreciated. Thank you. [Alexis / Poker Reflex Team]